Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7300fb2e0a3c78d72f6496979730c6a94bda458816664f9a303bfc6b3220e5c6

Tx prefix hash: b30d340d3570dcf0bbb5ec87a4d4c56d7bd0895bae64c56ddb971ae21e0dc037
Tx public key: b1bac9c61a83cabf2e5a1ee86dab676be0b37b063bd435c250a9899ad67ac93a
Timestamp: 1714652774 Timestamp [UCT]: 2024-05-02 12:26:14 Age [y:d:h:m:s]: 01:014:07:58:53
Block: 1013230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271173 RingCT/type: yes/0
Extra: 01b1bac9c61a83cabf2e5a1ee86dab676be0b37b063bd435c250a9899ad67ac93a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 461fc39998cb213d282c9eca1e0d9be77f59c3a6f409134cd45b61b272059da0 0.600000000000 1475993 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": 1013240, "vin": [ { "gen": { "height": 1013230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461fc39998cb213d282c9eca1e0d9be77f59c3a6f409134cd45b61b272059da0" } } ], "extra": [ 1, 177, 186, 201, 198, 26, 131, 202, 191, 46, 90, 30, 232, 109, 171, 103, 107, 224, 179, 123, 6, 59, 212, 53, 194, 80, 169, 137, 154, 214, 122, 201, 58, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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