Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07234be58c0a54a7cfbb426580016cc258a1eb93aa4655f9c2ed7ee40cf0a644

Tx prefix hash: 838fcd6be22dfabf11b5436c94ce9431ba09ec083a01da8be43fb4bc3be7c91e
Tx public key: f1aac2ed0bee9ee2a931182f001a844d30c7478de322d819030dd6c9af0b1556
Timestamp: 1758201836 Timestamp [UCT]: 2025-09-18 13:23:56 Age [y:d:h:m:s]: 00:133:16:54:06
Block: 1371164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95555 RingCT/type: yes/0
Extra: 01f1aac2ed0bee9ee2a931182f001a844d30c7478de322d819030dd6c9af0b1556021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8ced3b8010922635f6342e4701a6836a62f7d183cd18af5f9bed2d429fca15f 0.600000000000 1859241 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": 1371174, "vin": [ { "gen": { "height": 1371164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8ced3b8010922635f6342e4701a6836a62f7d183cd18af5f9bed2d429fca15f" } } ], "extra": [ 1, 241, 170, 194, 237, 11, 238, 158, 226, 169, 49, 24, 47, 0, 26, 132, 77, 48, 199, 71, 141, 227, 34, 216, 25, 3, 13, 214, 201, 175, 11, 21, 86, 2, 17, 0, 0, 0, 7, 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