Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 545e628521f8f2886c801e5be23445462cb9b4c233a8a07b0816afb620f7327c

Tx prefix hash: b310cdb26c5745c5d767f6d2d97b5dacf7d484381de3c6ae962a5f5e87e12dfc
Tx public key: cc4c7f286d6a9b7fe105c46e7f4b543303071b4407dc0b5d08761a4154cb680b
Timestamp: 1709486334 Timestamp [UCT]: 2024-03-03 17:18:54 Age [y:d:h:m:s]: 01:311:02:32:15
Block: 970400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481157 RingCT/type: yes/0
Extra: 01cc4c7f286d6a9b7fe105c46e7f4b543303071b4407dc0b5d08761a4154cb680b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 338c351870a734c92d7580d145e407fc3760a7b2e03a7ff4764b18162c1735e9 0.600000000000 1430253 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": 970410, "vin": [ { "gen": { "height": 970400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338c351870a734c92d7580d145e407fc3760a7b2e03a7ff4764b18162c1735e9" } } ], "extra": [ 1, 204, 76, 127, 40, 109, 106, 155, 127, 225, 5, 196, 110, 127, 75, 84, 51, 3, 7, 27, 68, 7, 220, 11, 93, 8, 118, 26, 65, 84, 203, 104, 11, 2, 17, 0, 0, 0, 3, 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