Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54190913a716c6ecdd1402e71bfb5ca6972f9156700048476cca8f6829867ae8

Tx prefix hash: abc671f09ec947df6d5d64db8350df1c0120b5a8537e16d5e84c748dc3b28629
Tx public key: e8ab2f31c3a953cd85d243cee2b840d9c8b28acde3a8bbc3a9d42b7bf351d9b2
Timestamp: 1761380188 Timestamp [UCT]: 2025-10-25 08:16:28 Age [y:d:h:m:s]: 00:018:12:48:45
Block: 1397519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13245 RingCT/type: yes/0
Extra: 01e8ab2f31c3a953cd85d243cee2b840d9c8b28acde3a8bbc3a9d42b7bf351d9b20211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc11fb2d582a90076dcb6ee1d446398b9a2633edefde6feab34d320152097e33 0.600000000000 1885810 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": 1397529, "vin": [ { "gen": { "height": 1397519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc11fb2d582a90076dcb6ee1d446398b9a2633edefde6feab34d320152097e33" } } ], "extra": [ 1, 232, 171, 47, 49, 195, 169, 83, 205, 133, 210, 67, 206, 226, 184, 64, 217, 200, 178, 138, 205, 227, 168, 187, 195, 169, 212, 43, 123, 243, 81, 217, 178, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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