Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f806ff3e57b9c43f99ffc1f85d56c69bbe1e5daae9de82a68230db14010f153d

Tx prefix hash: 833cab5b68a786d38882f46d9b2399658f2af97f629784c932d525404f6ee3c6
Tx public key: 8fe7a1a2bc1b075acbb7ce7626fb9aa34ed51e4849da9ce37a01be1e272809f1
Timestamp: 1752036743 Timestamp [UCT]: 2025-07-09 04:52:23 Age [y:d:h:m:s]: 00:140:10:15:56
Block: 1321732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98884 RingCT/type: yes/0
Extra: 018fe7a1a2bc1b075acbb7ce7626fb9aa34ed51e4849da9ce37a01be1e272809f102110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6739a79d98ab99bddc88fc0e012b5b2e137a535cfdae57f74e510afe569988bc 0.600000000000 1809441 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": 1321742, "vin": [ { "gen": { "height": 1321732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6739a79d98ab99bddc88fc0e012b5b2e137a535cfdae57f74e510afe569988bc" } } ], "extra": [ 1, 143, 231, 161, 162, 188, 27, 7, 90, 203, 183, 206, 118, 38, 251, 154, 163, 78, 213, 30, 72, 73, 218, 156, 227, 122, 1, 190, 30, 39, 40, 9, 241, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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