Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7a385160303d2f3438e4f0ee99524130cbedaa3b47b1e38342be3b03ed3d94

Tx prefix hash: d6c4c4d2984d8f88f7b563a43eaf5818c06a6f99240891b7255f2e87def2af81
Tx public key: 017584171b0c8d4208ac325ee551f29ff71c7bdb23c1670d0633e5a22466e3ef
Timestamp: 1585242697 Timestamp [UCT]: 2020-03-26 17:11:37 Age [y:d:h:m:s]: 04:312:05:34:09
Block: 88599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120774 RingCT/type: yes/0
Extra: 01017584171b0c8d4208ac325ee551f29ff71c7bdb23c1670d0633e5a22466e3ef02110000000339be35fb000000000000000000

1 output(s) for total of 312.201877993000 dcy

stealth address amount amount idx
00: a3c1b60bdd48ec96184bbd3f8bcebc0ec812bd2477823bdd7448fc85e28ccacf 312.201877993000 159179 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": 88609, "vin": [ { "gen": { "height": 88599 } } ], "vout": [ { "amount": 312201877993, "target": { "key": "a3c1b60bdd48ec96184bbd3f8bcebc0ec812bd2477823bdd7448fc85e28ccacf" } } ], "extra": [ 1, 1, 117, 132, 23, 27, 12, 141, 66, 8, 172, 50, 94, 229, 81, 242, 159, 247, 28, 123, 219, 35, 193, 103, 13, 6, 51, 229, 162, 36, 102, 227, 239, 2, 17, 0, 0, 0, 3, 57, 190, 53, 251, 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