Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e64781ec935da327cf36b676ede91fb3db361c5a1deb417511e07b1cc3f45b89

Tx prefix hash: e2797284778d64f841c95c8fd4bb10f7b9ab02877d2dc4915ca6fcb714992d9c
Tx public key: 68c0196ff484d64164a57a66ec57554e5876ef4b7de75f1da7228e520a1cbef8
Timestamp: 1632818098 Timestamp [UCT]: 2021-09-28 08:34:58 Age [y:d:h:m:s]: 03:148:10:00:50
Block: 342388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 882572 RingCT/type: yes/0
Extra: 0168c0196ff484d64164a57a66ec57554e5876ef4b7de75f1da7228e520a1cbef80211000000268d0de867000000000000000000

1 output(s) for total of 45.032582695000 dcy

stealth address amount amount idx
00: 1bf1700694f8b21cebc5f749ca314d83ee2cf257b6593ecb2a6e1df616db9b6a 45.032582695000 703110 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": 342398, "vin": [ { "gen": { "height": 342388 } } ], "vout": [ { "amount": 45032582695, "target": { "key": "1bf1700694f8b21cebc5f749ca314d83ee2cf257b6593ecb2a6e1df616db9b6a" } } ], "extra": [ 1, 104, 192, 25, 111, 244, 132, 214, 65, 100, 165, 122, 102, 236, 87, 85, 78, 88, 118, 239, 75, 125, 231, 95, 29, 167, 34, 142, 82, 10, 28, 190, 248, 2, 17, 0, 0, 0, 38, 141, 13, 232, 103, 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