Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 323f007340d3a51114e4dd803847f3821f79a9cdcc1c565ab05b632757aa5e44

Tx prefix hash: 0c416cf44fec0ed7b302c91a8deaf597a206df48a3a41a2ba88f53e7d4e4ac7b
Tx public key: c306ea2a08a2a1862d6f99341e549498aee0ab6b1920b6a615c2f8b92557828f
Timestamp: 1685099639 Timestamp [UCT]: 2023-05-26 11:13:59 Age [y:d:h:m:s]: 01:324:11:29:38
Block: 768466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493105 RingCT/type: yes/0
Extra: 01c306ea2a08a2a1862d6f99341e549498aee0ab6b1920b6a615c2f8b92557828f021100000001b3164c24000000000000000000

1 output(s) for total of 1.744830775000 dcy

stealth address amount amount idx
00: 1ba98be8a12bb28dc2d0f8b2a08d8c60c79e9b848f0f8fcc66cdb60c43ce871c 1.744830775000 1217667 of 0

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": 768476, "vin": [ { "gen": { "height": 768466 } } ], "vout": [ { "amount": 1744830775, "target": { "key": "1ba98be8a12bb28dc2d0f8b2a08d8c60c79e9b848f0f8fcc66cdb60c43ce871c" } } ], "extra": [ 1, 195, 6, 234, 42, 8, 162, 161, 134, 45, 111, 153, 52, 30, 84, 148, 152, 174, 224, 171, 107, 25, 32, 182, 166, 21, 194, 248, 185, 37, 87, 130, 143, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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