Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa2cfe1a6b25aabb1086774a276b8dff54a7e21e5308961b4fbf2d96a37a437

Tx prefix hash: e1aeb17853f2f6614f05d4994a10bb91c08ba83cbaba57820edbb45167de943f
Tx public key: f80288c63bceb3a16e603a710babe7855631db1305b4eb0fef74140791a5dc90
Timestamp: 1646541734 Timestamp [UCT]: 2022-03-06 04:42:14 Age [y:d:h:m:s]: 03:240:08:17:51
Block: 452309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 949633 RingCT/type: yes/0
Extra: 01f80288c63bceb3a16e603a710babe7855631db1305b4eb0fef74140791a5dc9002110000000b4a0f5013000000000000000000

1 output(s) for total of 19.467617113000 dcy

stealth address amount amount idx
00: 5016bbd9f081b393acfff268a9ea5c6dc455e0348a5fc18680cd5b94a439bc9d 19.467617113000 867600 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": 452319, "vin": [ { "gen": { "height": 452309 } } ], "vout": [ { "amount": 19467617113, "target": { "key": "5016bbd9f081b393acfff268a9ea5c6dc455e0348a5fc18680cd5b94a439bc9d" } } ], "extra": [ 1, 248, 2, 136, 198, 59, 206, 179, 161, 110, 96, 58, 113, 11, 171, 231, 133, 86, 49, 219, 19, 5, 180, 235, 15, 239, 116, 20, 7, 145, 165, 220, 144, 2, 17, 0, 0, 0, 11, 74, 15, 80, 19, 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