Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d42a3697db76e4f39378fc64584e8fc1d67183b8715b7231ede5e786a181277

Tx prefix hash: 44ed4db345708ac32a3f3f02b946325e04841b032746d57b0fe536b3dae24e0f
Tx public key: 8128904d98c892a3623126599e99d7ccd500f883c55eb1d10e5079c0f7f58217
Timestamp: 1711670994 Timestamp [UCT]: 2024-03-29 00:09:54 Age [y:d:h:m:s]: 01:055:23:07:20
Block: 988524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300980 RingCT/type: yes/0
Extra: 018128904d98c892a3623126599e99d7ccd500f883c55eb1d10e5079c0f7f582170211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6a8c355a2278b5eadd268d7c6ec4284b46ec714b8d6576083ebf7eb67a7d2c 0.600000000000 1448803 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": 988534, "vin": [ { "gen": { "height": 988524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6a8c355a2278b5eadd268d7c6ec4284b46ec714b8d6576083ebf7eb67a7d2c" } } ], "extra": [ 1, 129, 40, 144, 77, 152, 200, 146, 163, 98, 49, 38, 89, 158, 153, 215, 204, 213, 0, 248, 131, 197, 94, 177, 209, 14, 80, 121, 192, 247, 245, 130, 23, 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