Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae3fdcfbc80ba30fcf77f2ae2a8cfa03517b28946d0231dc4ac6c2a220e4088a

Tx prefix hash: 6395c100bc6737c6f309aa180a12580c826d6ce8de2e86ae889974fa37c3f9fb
Tx public key: d808108f41a34bbf78c3fda940f1bb77aae0ad753550f45442571965f506157b
Timestamp: 1760558814 Timestamp [UCT]: 2025-10-15 20:06:54 Age [y:d:h:m:s]: 00:103:19:59:24
Block: 1390690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74173 RingCT/type: yes/0
Extra: 01d808108f41a34bbf78c3fda940f1bb77aae0ad753550f45442571965f506157b0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5ab754f8c7e41acef63b7e5fcd657fa879a6f80ebb8c1cb6ead2f166ef7d24d 0.600000000000 1878937 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": 1390700, "vin": [ { "gen": { "height": 1390690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5ab754f8c7e41acef63b7e5fcd657fa879a6f80ebb8c1cb6ead2f166ef7d24d" } } ], "extra": [ 1, 216, 8, 16, 143, 65, 163, 75, 191, 120, 195, 253, 169, 64, 241, 187, 119, 170, 224, 173, 117, 53, 80, 244, 84, 66, 87, 25, 101, 245, 6, 21, 123, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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