Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b837ff20c848c649511781840412f988f1de36630f09c15c3fb1cb4dc441ab63

Tx prefix hash: 4e5dc6f016342c9432202dee247ba25af5941c5f176d2facd0e6f80ed1a6692a
Tx public key: 960fd02966eb4a68daa4d0527a2f4fcac15777da9bd16d7c7c01b03ed5f28d26
Timestamp: 1578981796 Timestamp [UCT]: 2020-01-14 06:03:16 Age [y:d:h:m:s]: 05:087:22:16:23
Block: 45162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213014 RingCT/type: yes/0
Extra: 01960fd02966eb4a68daa4d0527a2f4fcac15777da9bd16d7c7c01b03ed5f28d2602110000000d4943cd9f000000000000000000

1 output(s) for total of 434.870939275000 dcy

stealth address amount amount idx
00: fb60f78278be6517afb795ed7a014a93f8afa50429da0730851b30177bfb6733 434.870939275000 82418 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": 45172, "vin": [ { "gen": { "height": 45162 } } ], "vout": [ { "amount": 434870939275, "target": { "key": "fb60f78278be6517afb795ed7a014a93f8afa50429da0730851b30177bfb6733" } } ], "extra": [ 1, 150, 15, 208, 41, 102, 235, 74, 104, 218, 164, 208, 82, 122, 47, 79, 202, 193, 87, 119, 218, 155, 209, 109, 124, 124, 1, 176, 62, 213, 242, 141, 38, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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