Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a53dd13cb95cce1b27165512717d85292c2eb37bcec427c750322d3ee8f2d2d4

Tx prefix hash: 78d95640f9bf63b462e1ea941755f28ab3978775823f91b71dfbb677d775c45e
Tx public key: 7cbc8c46f81783f3a7c827e87c3a403578c075ac1b30b231b4809831ba8906d2
Timestamp: 1755805998 Timestamp [UCT]: 2025-08-21 19:53:18 Age [y:d:h:m:s]: 00:047:23:13:49
Block: 1351484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34160 RingCT/type: yes/0
Extra: 017cbc8c46f81783f3a7c827e87c3a403578c075ac1b30b231b4809831ba8906d202110000000ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6763f16477dd69b7216c9e7f2a90143d6a7cdd0794c26d84b740fc3bbc9fe02a 0.600000000000 1839437 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": 1351494, "vin": [ { "gen": { "height": 1351484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6763f16477dd69b7216c9e7f2a90143d6a7cdd0794c26d84b740fc3bbc9fe02a" } } ], "extra": [ 1, 124, 188, 140, 70, 248, 23, 131, 243, 167, 200, 39, 232, 124, 58, 64, 53, 120, 192, 117, 172, 27, 48, 178, 49, 180, 128, 152, 49, 186, 137, 6, 210, 2, 17, 0, 0, 0, 10, 178, 247, 132, 196, 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