Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a0849719fb787da415494a17f1495a4d72badf4c482669f9c6b4b4db3673df

Tx prefix hash: 27051b54563fa06571a5f32d14bcd4ebe421d1eee998a34fee0c7726377c46e0
Tx public key: 0a0853d58d0fd4cbe7ebbb9a770d4da8dfeddc056b5ade21658873642e1b104d
Timestamp: 1706502388 Timestamp [UCT]: 2024-01-29 04:26:28 Age [y:d:h:m:s]: 01:071:23:55:11
Block: 945630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312546 RingCT/type: yes/0
Extra: 010a0853d58d0fd4cbe7ebbb9a770d4da8dfeddc056b5ade21658873642e1b104d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 555c75fbca09e0810dd5506fd1a7aed47e891bd7f691cc60fcd7ee4680d8fcb4 0.600000000000 1403946 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": 945640, "vin": [ { "gen": { "height": 945630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "555c75fbca09e0810dd5506fd1a7aed47e891bd7f691cc60fcd7ee4680d8fcb4" } } ], "extra": [ 1, 10, 8, 83, 213, 141, 15, 212, 203, 231, 235, 187, 154, 119, 13, 77, 168, 223, 237, 220, 5, 107, 90, 222, 33, 101, 136, 115, 100, 46, 27, 16, 77, 2, 17, 0, 0, 0, 5, 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