Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f187955cbbc0dd9919fb6079fd1055e88024ce545aaa3485d3d329cb3489ad53

Tx prefix hash: a22aa9326e307275958f282ad38d2d1f2fc7bbe5d658d1ba9e59de4d01a3ff36
Tx public key: 08a4fe857d523c6b0c617fffc2d7b5fc37b9b816d528104fc6815d2f92f93dab
Timestamp: 1705585430 Timestamp [UCT]: 2024-01-18 13:43:50 Age [y:d:h:m:s]: 01:151:21:19:32
Block: 938034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369580 RingCT/type: yes/0
Extra: 0108a4fe857d523c6b0c617fffc2d7b5fc37b9b816d528104fc6815d2f92f93dab02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76654353737fdefa8840b12a36914e6e0584f237fa33cceaf014466f55d7386c 0.600000000000 1396098 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": 938044, "vin": [ { "gen": { "height": 938034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76654353737fdefa8840b12a36914e6e0584f237fa33cceaf014466f55d7386c" } } ], "extra": [ 1, 8, 164, 254, 133, 125, 82, 60, 107, 12, 97, 127, 255, 194, 215, 181, 252, 55, 185, 184, 22, 213, 40, 16, 79, 198, 129, 93, 47, 146, 249, 61, 171, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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