Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ba7e3bdd71ea27c48450f5253c1b554280a9b387a618de2572f1ec17cf0045c

Tx prefix hash: 7b869d0885866e9b54724e6daae6faeb478534bc73c89b8664e81a05e5af73c1
Tx public key: 449e81fdf590b5b1aaefe2a327d01254acdace2089be29f23ed47277d9151a1a
Timestamp: 1715278323 Timestamp [UCT]: 2024-05-09 18:12:03 Age [y:d:h:m:s]: 01:027:09:53:32
Block: 1018411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280531 RingCT/type: yes/0
Extra: 01449e81fdf590b5b1aaefe2a327d01254acdace2089be29f23ed47277d9151a1a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 343cea1deeec60de18f643d79535bc15e8a83fdcaeb3dde5813ec0d7ea5174b8 0.600000000000 1482200 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": 1018421, "vin": [ { "gen": { "height": 1018411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "343cea1deeec60de18f643d79535bc15e8a83fdcaeb3dde5813ec0d7ea5174b8" } } ], "extra": [ 1, 68, 158, 129, 253, 245, 144, 181, 177, 170, 239, 226, 163, 39, 208, 18, 84, 172, 218, 206, 32, 137, 190, 41, 242, 62, 212, 114, 119, 217, 21, 26, 26, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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