Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9a3e0ff2636c199c7c600e63d04f366a4a0bf549a89d848de812c29138a97df

Tx prefix hash: 008b7fd0ba1771fadd9f4a7a4d830679f80055e232e2ca7a090348cf748174f3
Tx public key: 30536a57e4bf34e210d51eca271223fc38f7c31ff0ede531e3bb3977d01404f5
Timestamp: 1577710772 Timestamp [UCT]: 2019-12-30 12:59:32 Age [y:d:h:m:s]: 05:003:11:58:53
Block: 35031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152495 RingCT/type: yes/0
Extra: 0130536a57e4bf34e210d51eca271223fc38f7c31ff0ede531e3bb3977d01404f50211000000034ac5aa02000000000000000000

1 output(s) for total of 469.816872874000 dcy

stealth address amount amount idx
00: d2826dc39976935e1e283e8c1bc2259b79862911118b5b9cbb48bc113831f3b4 469.816872874000 59016 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": 35041, "vin": [ { "gen": { "height": 35031 } } ], "vout": [ { "amount": 469816872874, "target": { "key": "d2826dc39976935e1e283e8c1bc2259b79862911118b5b9cbb48bc113831f3b4" } } ], "extra": [ 1, 48, 83, 106, 87, 228, 191, 52, 226, 16, 213, 30, 202, 39, 18, 35, 252, 56, 247, 195, 31, 240, 237, 229, 49, 227, 187, 57, 119, 208, 20, 4, 245, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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