Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 615a44210d482b513c7f01c956399fd360445d7b4289d7afba4e7ded7c01685c

Tx prefix hash: 555a0ca15d81c86ce5d192d47e2621978f1c3ba0fe92c549e1a107e496644c87
Tx public key: 00adbc7e02609d8d17c921e9649c15d9db50915a7ffe83c9b9d0f4bfe5e5c37e
Timestamp: 1580897469 Timestamp [UCT]: 2020-02-05 10:11:09 Age [y:d:h:m:s]: 04:299:01:35:08
Block: 59248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104994 RingCT/type: yes/0
Extra: 0100adbc7e02609d8d17c921e9649c15d9db50915a7ffe83c9b9d0f4bfe5e5c37e0211000000014ac5aa02000000000000000000

1 output(s) for total of 390.559854624000 dcy

stealth address amount amount idx
00: d362cffd420d547cf42733428c4e8aa2e6c02039cb4339baf62054f05b1b4d16 390.559854624000 109366 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": 59258, "vin": [ { "gen": { "height": 59248 } } ], "vout": [ { "amount": 390559854624, "target": { "key": "d362cffd420d547cf42733428c4e8aa2e6c02039cb4339baf62054f05b1b4d16" } } ], "extra": [ 1, 0, 173, 188, 126, 2, 96, 157, 141, 23, 201, 33, 233, 100, 156, 21, 217, 219, 80, 145, 90, 127, 254, 131, 201, 185, 208, 244, 191, 229, 229, 195, 126, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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