Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abc5ba18076993cf4ffd88f72fe8cb2ba6895dce6a84966baf9ee8692fb19e70

Tx prefix hash: 9511957e894dcba350810430cff5ee8a348d00320da791faf2c0820cd5efcbd7
Tx public key: d0a7c175663db03cddcba7e9b08f99737a51853e2d6b7010cf60a523fde60e69
Timestamp: 1736758361 Timestamp [UCT]: 2025-01-13 08:52:41 Age [y:d:h:m:s]: 00:065:02:30:22
Block: 1196352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46318 RingCT/type: yes/0
Extra: 01d0a7c175663db03cddcba7e9b08f99737a51853e2d6b7010cf60a523fde60e69021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ab48c90bd672c4b5fd09b6ec88bf9b853af66112450749f54df3c423a000c27 0.600000000000 1682951 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": 1196362, "vin": [ { "gen": { "height": 1196352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ab48c90bd672c4b5fd09b6ec88bf9b853af66112450749f54df3c423a000c27" } } ], "extra": [ 1, 208, 167, 193, 117, 102, 61, 176, 60, 221, 203, 167, 233, 176, 143, 153, 115, 122, 81, 133, 62, 45, 107, 112, 16, 207, 96, 165, 35, 253, 230, 14, 105, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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