Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 39d7266ed153a0910db4a79cbdec26c8f97c9337efd24509b498f56e9ed96e41

Tx prefix hash: 51572fd03d3975bed98491560f4b5863e91b335971b11fbf9573034d5212281e
Tx public key: 8a86dfa7fafb54f2adde4f0c442fb4c04140d4c96bf2d7f11c011282e341c2e3
Timestamp: 1742241536 Timestamp [UCT]: 2025-03-17 19:58:56 Age [y:d:h:m:s]: 00:239:04:39:27
Block: 1241501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168663 RingCT/type: yes/0
Extra: 018a86dfa7fafb54f2adde4f0c442fb4c04140d4c96bf2d7f11c011282e341c2e302110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248f420c880f083fe507f13232f8b4516c26a45c3a3c513120bfc0175eeafffc 0.600000000000 1728474 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1241511, "vin": [ { "gen": { "height": 1241501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248f420c880f083fe507f13232f8b4516c26a45c3a3c513120bfc0175eeafffc" } } ], "extra": [ 1, 138, 134, 223, 167, 250, 251, 84, 242, 173, 222, 79, 12, 68, 47, 180, 192, 65, 64, 212, 201, 107, 242, 215, 241, 28, 1, 18, 130, 227, 65, 194, 227, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8