Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fae79ab9dd2ac2a2a5c719d03eb4d879e4ef700bd201307fa564516330c22e2

Tx prefix hash: 496d7525174dda66a98d49b7fdbc14dd773a9d0d1372f1888444e61b435b498a
Tx public key: c41e2bf5df0b0ef79bd91c7b90fa83feb204cebb3a7bda0655225f02855855ff
Timestamp: 1633206506 Timestamp [UCT]: 2021-10-02 20:28:26 Age [y:d:h:m:s]: 03:086:03:37:59
Block: 345362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 838568 RingCT/type: yes/0
Extra: 01c41e2bf5df0b0ef79bd91c7b90fa83feb204cebb3a7bda0655225f02855855ff02110000001036fe6557000000000000000000

1 output(s) for total of 44.022302846000 dcy

stealth address amount amount idx
00: e61aa9daf29abc59967dce4a9f28e2e16acfde0cb11b5abd03ba87e52911ea80 44.022302846000 708498 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": 345372, "vin": [ { "gen": { "height": 345362 } } ], "vout": [ { "amount": 44022302846, "target": { "key": "e61aa9daf29abc59967dce4a9f28e2e16acfde0cb11b5abd03ba87e52911ea80" } } ], "extra": [ 1, 196, 30, 43, 245, 223, 11, 14, 247, 155, 217, 28, 123, 144, 250, 131, 254, 178, 4, 206, 187, 58, 123, 218, 6, 85, 34, 95, 2, 133, 88, 85, 255, 2, 17, 0, 0, 0, 16, 54, 254, 101, 87, 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