Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469b46679d5fb1a547536b5c26fbb58e1ce12a877522e5491f37378d90531b0d

Tx prefix hash: 456ad0463dbf75444d97f042efdffb82e63859dd234f16376bb0ffaff85b5e13
Tx public key: 7a6ef43762e7904b5b1888c29975ea0aa6a764e6251e1a0785ef3b0d041bc26c
Timestamp: 1640541435 Timestamp [UCT]: 2021-12-26 17:57:15 Age [y:d:h:m:s]: 03:140:12:18:18
Block: 404022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 879250 RingCT/type: yes/0
Extra: 017a6ef43762e7904b5b1888c29975ea0aa6a764e6251e1a0785ef3b0d041bc26c02110000000106faf294000000000000000000

1 output(s) for total of 28.138940556000 dcy

stealth address amount amount idx
00: 55b22e67461e8990a0a11d5e1a5830647061b89991754a17eab201536f966871 28.138940556000 804013 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": 404032, "vin": [ { "gen": { "height": 404022 } } ], "vout": [ { "amount": 28138940556, "target": { "key": "55b22e67461e8990a0a11d5e1a5830647061b89991754a17eab201536f966871" } } ], "extra": [ 1, 122, 110, 244, 55, 98, 231, 144, 75, 91, 24, 136, 194, 153, 117, 234, 10, 166, 167, 100, 230, 37, 30, 26, 7, 133, 239, 59, 13, 4, 27, 194, 108, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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