Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b058164f7f6c093110c1e78b8214f4219480f6eff925c3c2e102acd5847f9587

Tx prefix hash: 11d7f7e72f753ccfe84a71662d7b493a0c3cac1f4ed4f0e1842f05d7c36f494a
Tx public key: 4357278dc70e48acc6e580e5a65116fe03511114a51980f04e461ebf43ceb21f
Timestamp: 1762688041 Timestamp [UCT]: 2025-11-09 11:34:01 Age [y:d:h:m:s]: 00:018:19:20:25
Block: 1408340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13461 RingCT/type: yes/0
Extra: 014357278dc70e48acc6e580e5a65116fe03511114a51980f04e461ebf43ceb21f021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c0420ffb42979598086cc014b275d2b4f0e6a6cae751c90af0ddb8922d80cd 0.600000000000 1896769 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": 1408350, "vin": [ { "gen": { "height": 1408340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c0420ffb42979598086cc014b275d2b4f0e6a6cae751c90af0ddb8922d80cd" } } ], "extra": [ 1, 67, 87, 39, 141, 199, 14, 72, 172, 198, 229, 128, 229, 166, 81, 22, 254, 3, 81, 17, 20, 165, 25, 128, 240, 78, 70, 30, 191, 67, 206, 178, 31, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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