Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a84cbbb137f54f2b8135b116fb5bb6d64cc8fad7cf12bcf75ca16075c1524a32

Tx prefix hash: bfccec332e2392c1daf58a318a7dca0eaee6caf8967db4b424fa7f91557bae50
Tx public key: 79bcbb32ff582f333ef8a11eb512f9240f09054cc1d1b0a789544e07f6f7bcd2
Timestamp: 1750604348 Timestamp [UCT]: 2025-06-22 14:59:08 Age [y:d:h:m:s]: 00:149:11:56:55
Block: 1310514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104723 RingCT/type: yes/0
Extra: 0179bcbb32ff582f333ef8a11eb512f9240f09054cc1d1b0a789544e07f6f7bcd202110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cfa071ec2888c204105e53fe31cdb2e429aa3399e36074ba5e0f7fb1d905a98 0.600000000000 1798135 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": 1310524, "vin": [ { "gen": { "height": 1310514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cfa071ec2888c204105e53fe31cdb2e429aa3399e36074ba5e0f7fb1d905a98" } } ], "extra": [ 1, 121, 188, 187, 50, 255, 88, 47, 51, 62, 248, 161, 30, 181, 18, 249, 36, 15, 9, 5, 76, 193, 209, 176, 167, 137, 84, 78, 7, 246, 247, 188, 210, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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