Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b4cc9d93de89ce901fe03e361c81869e70c03815c1c98f4c8474c958d89581

Tx prefix hash: c3ec6ac20e2e014bf2c960c6052c73c9d40fbd30175b208b0e7e13ea90a95ab8
Tx public key: d5576b7a596248790444d69abcdb4190d5940425399e37f643bf73afe6f51a1e
Timestamp: 1706304655 Timestamp [UCT]: 2024-01-26 21:30:55 Age [y:d:h:m:s]: 01:098:08:29:00
Block: 943984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331402 RingCT/type: yes/0
Extra: 01d5576b7a596248790444d69abcdb4190d5940425399e37f643bf73afe6f51a1e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae434caa1c286383f0cee3fe05839bcf082cda315744bea134e5011e8f7b6a0 0.600000000000 1402210 of 15

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": 943994, "vin": [ { "gen": { "height": 943984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae434caa1c286383f0cee3fe05839bcf082cda315744bea134e5011e8f7b6a0" } } ], "extra": [ 1, 213, 87, 107, 122, 89, 98, 72, 121, 4, 68, 214, 154, 188, 219, 65, 144, 213, 148, 4, 37, 57, 158, 55, 246, 67, 191, 115, 175, 230, 245, 26, 30, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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