Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ddf3ea2e175c34321762406564d0833aa857fb07d2bb63dfcf99750a33c3dec

Tx prefix hash: 4ff0e0525d8676956ad0b4052c794e99c78d9108a333d0887bd22324649bf31a
Tx public key: 0075a4d094034e274a0cfcbbda53e3bf2eae8a0612a9d05d5d3d428edc58e131
Timestamp: 1705344211 Timestamp [UCT]: 2024-01-15 18:43:31 Age [y:d:h:m:s]: 01:107:09:05:50
Block: 936031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337866 RingCT/type: yes/0
Extra: 010075a4d094034e274a0cfcbbda53e3bf2eae8a0612a9d05d5d3d428edc58e1310211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c292308e078b005bf20719f2a2358479cb47826685ff343f37ce04fa56cd2c7 0.600000000000 1394053 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": 936041, "vin": [ { "gen": { "height": 936031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c292308e078b005bf20719f2a2358479cb47826685ff343f37ce04fa56cd2c7" } } ], "extra": [ 1, 0, 117, 164, 208, 148, 3, 78, 39, 74, 12, 252, 187, 218, 83, 227, 191, 46, 174, 138, 6, 18, 169, 208, 93, 93, 61, 66, 142, 220, 88, 225, 49, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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