Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8d80ab780868d160890b73793b561eb7c1b1ebc2ae6b6c65c004c3520b51fad

Tx prefix hash: c7579ae53a44e2fb6e9694e32787bb45e39c8c74aeaed0ea51e37ee32c3a00e1
Tx public key: 5dae27c8e03bf8106e03f8443ba27421cabe7759c0045ad44ca57517ca051e17
Timestamp: 1584920879 Timestamp [UCT]: 2020-03-22 23:47:59 Age [y:d:h:m:s]: 05:200:19:31:20
Block: 86808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1298843 RingCT/type: yes/0
Extra: 015dae27c8e03bf8106e03f8443ba27421cabe7759c0045ad44ca57517ca051e17021100000011e5e30634000000000000000000

1 output(s) for total of 316.497176694000 dcy

stealth address amount amount idx
00: 74b09351ddfe91bdc258d0f67b5ab8f5115a629ba9403a84ff4d734aacda2911 316.497176694000 156616 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": 86818, "vin": [ { "gen": { "height": 86808 } } ], "vout": [ { "amount": 316497176694, "target": { "key": "74b09351ddfe91bdc258d0f67b5ab8f5115a629ba9403a84ff4d734aacda2911" } } ], "extra": [ 1, 93, 174, 39, 200, 224, 59, 248, 16, 110, 3, 248, 68, 59, 162, 116, 33, 202, 190, 119, 89, 192, 4, 90, 212, 76, 165, 117, 23, 202, 5, 30, 23, 2, 17, 0, 0, 0, 17, 229, 227, 6, 52, 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