Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd4b7dcf0606e8dcdf726fdb75352385bb482c44c970ed75c0225ba51e4e80b

Tx prefix hash: d36af88e933381303040773c1947d222e2f2367a869b245ec26c4f7941b955e2
Tx public key: f8949f7002d8678b68cdb77bf037eddb28c8a1f8c515bec6ef76da9e9a7e24d5
Timestamp: 1760456000 Timestamp [UCT]: 2025-10-14 15:33:20 Age [y:d:h:m:s]: 00:026:03:22:33
Block: 1389836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18719 RingCT/type: yes/0
Extra: 01f8949f7002d8678b68cdb77bf037eddb28c8a1f8c515bec6ef76da9e9a7e24d50211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c73fea33fcd57031e98d2e07946a3ae8e75a6b9491b422037878eccf57e6d89 0.600000000000 1878065 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": 1389846, "vin": [ { "gen": { "height": 1389836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c73fea33fcd57031e98d2e07946a3ae8e75a6b9491b422037878eccf57e6d89" } } ], "extra": [ 1, 248, 148, 159, 112, 2, 216, 103, 139, 104, 205, 183, 123, 240, 55, 237, 219, 40, 200, 161, 248, 197, 21, 190, 198, 239, 118, 218, 158, 154, 126, 36, 213, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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