Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54333a9b116f72f9c41846d3f3ad6fa0292e513cc1d62cf2137e5f05fae01bda

Tx prefix hash: f25d4026f452cd0e319674225f2aefb9410fd0aa13c0cc61e7bd4c05c29a5476
Tx public key: 224802171619de30c4b3aedd8831e06f02a15e1e8311927f5009f1a48cd0e654
Timestamp: 1673193671 Timestamp [UCT]: 2023-01-08 16:01:11 Age [y:d:h:m:s]: 02:011:02:17:24
Block: 670357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529816 RingCT/type: yes/0
Extra: 01224802171619de30c4b3aedd8831e06f02a15e1e8311927f5009f1a48cd0e65402110000000252542ceb000000000000000000

1 output(s) for total of 3.688372919000 dcy

stealth address amount amount idx
00: a169eddb7b353c7411b831a16e85c28902e27ca9e365b4ff81eb9b17efd96538 3.688372919000 1111756 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": 670367, "vin": [ { "gen": { "height": 670357 } } ], "vout": [ { "amount": 3688372919, "target": { "key": "a169eddb7b353c7411b831a16e85c28902e27ca9e365b4ff81eb9b17efd96538" } } ], "extra": [ 1, 34, 72, 2, 23, 22, 25, 222, 48, 196, 179, 174, 221, 136, 49, 224, 111, 2, 161, 94, 30, 131, 17, 146, 127, 80, 9, 241, 164, 140, 208, 230, 84, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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