Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d7167a0510e5d4e0c5e79e0fdbf266fbd220a8fc4e9808bd2aa65a867aec3fd

Tx prefix hash: 67941bc76db4b5efc3940b216b70cee7629159382d546be80baff08fd74e5e04
Tx public key: 9800537f8ef3a329c19029220d157aa5c1335263283c5ee0d1adb17f2d551ae0
Timestamp: 1727524186 Timestamp [UCT]: 2024-09-28 11:49:46 Age [y:d:h:m:s]: 00:063:21:34:34
Block: 1119940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45673 RingCT/type: yes/0
Extra: 019800537f8ef3a329c19029220d157aa5c1335263283c5ee0d1adb17f2d551ae002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39cd6b81c10950ff10ee0bc0659a56aa86987f8b2da231dc7766bf9f8f6deb24 0.600000000000 1601679 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": 1119950, "vin": [ { "gen": { "height": 1119940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39cd6b81c10950ff10ee0bc0659a56aa86987f8b2da231dc7766bf9f8f6deb24" } } ], "extra": [ 1, 152, 0, 83, 127, 142, 243, 163, 41, 193, 144, 41, 34, 13, 21, 122, 165, 193, 51, 82, 99, 40, 60, 94, 224, 209, 173, 177, 127, 45, 85, 26, 224, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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