Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b27b91a42541298cbf244385fb28b75ba0fc462763af73669c6e70aa4e1b1d2

Tx prefix hash: 6068d2414b4c5bbfb383b06db4bc6632b8f9bb43fd4cf8d245b4e17fe6a9a955
Tx public key: 506b37874c4e0d2ce1aa1b6086ecfda08fbcfe0edc618816961b9e3883ff84dd
Timestamp: 1672892572 Timestamp [UCT]: 2023-01-05 04:22:52 Age [y:d:h:m:s]: 02:023:08:27:11
Block: 667866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538377 RingCT/type: yes/0
Extra: 01506b37874c4e0d2ce1aa1b6086ecfda08fbcfe0edc618816961b9e3883ff84dd02110000000275e3f0e9000000000000000000

1 output(s) for total of 3.759089431000 dcy

stealth address amount amount idx
00: c13ea3463a42efcd9f11fc1be399f010454e4cd0da78f8b5df5ba836d079a105 3.759089431000 1109085 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": 667876, "vin": [ { "gen": { "height": 667866 } } ], "vout": [ { "amount": 3759089431, "target": { "key": "c13ea3463a42efcd9f11fc1be399f010454e4cd0da78f8b5df5ba836d079a105" } } ], "extra": [ 1, 80, 107, 55, 135, 76, 78, 13, 44, 225, 170, 27, 96, 134, 236, 253, 160, 143, 188, 254, 14, 220, 97, 136, 22, 150, 27, 158, 56, 131, 255, 132, 221, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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