Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2767727fa49c902a348a2418be7f8043ee1b8d409894fe03d9b13e41e8cd1a3

Tx prefix hash: 5daa25a8d024ca11232f411d1d51b04c2c4c7c255e909ca2e56ca2d614d351bf
Tx public key: 4fb24df45d2d0dad9cfd2318cdd2a1ee0dc6dd813e936bd4a1a134bac7cd032e
Timestamp: 1648538723 Timestamp [UCT]: 2022-03-29 07:25:23 Age [y:d:h:m:s]: 02:236:21:02:29
Block: 468767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 688812 RingCT/type: yes/0
Extra: 014fb24df45d2d0dad9cfd2318cdd2a1ee0dc6dd813e936bd4a1a134bac7cd032e02110000000206faf294000000000000000000

1 output(s) for total of 17.170406851000 dcy

stealth address amount amount idx
00: a6ea240c0b2bd7a0543dc9df9424f918930eebae36d6cf08d5f1e8f1f6e0465e 17.170406851000 887551 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": 468777, "vin": [ { "gen": { "height": 468767 } } ], "vout": [ { "amount": 17170406851, "target": { "key": "a6ea240c0b2bd7a0543dc9df9424f918930eebae36d6cf08d5f1e8f1f6e0465e" } } ], "extra": [ 1, 79, 178, 77, 244, 93, 45, 13, 173, 156, 253, 35, 24, 205, 210, 161, 238, 13, 198, 221, 129, 62, 147, 107, 212, 161, 161, 52, 186, 199, 205, 3, 46, 2, 17, 0, 0, 0, 2, 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