Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba3cb2816743748fd061a817f9f6ef1aef1a7f7e3507aa2b6cb5466ef49dfd6

Tx prefix hash: 985a125b1c79af15f4bbe1a9ab2c59bb3a6df252cee958ad52889317841e5f78
Tx public key: d288fe68e0683fce0836c000d8143912c21f9409575ea40b31d699dcdb2d3fd6
Timestamp: 1694170864 Timestamp [UCT]: 2023-09-08 11:01:04 Age [y:d:h:m:s]: 01:129:12:04:50
Block: 843602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353883 RingCT/type: yes/0
Extra: 01d288fe68e0683fce0836c000d8143912c21f9409575ea40b31d699dcdb2d3fd6021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.983590003000 dcy

stealth address amount amount idx
00: 29a0f8069088c35bea0b712c58f9d054603cbb5701b2853ca3e7b85224446fbf 0.983590003000 1296848 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": 843612, "vin": [ { "gen": { "height": 843602 } } ], "vout": [ { "amount": 983590003, "target": { "key": "29a0f8069088c35bea0b712c58f9d054603cbb5701b2853ca3e7b85224446fbf" } } ], "extra": [ 1, 210, 136, 254, 104, 224, 104, 63, 206, 8, 54, 192, 0, 216, 20, 57, 18, 194, 31, 148, 9, 87, 94, 164, 11, 49, 214, 153, 220, 219, 45, 63, 214, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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