Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b30e2d9905eb57f874b3e56ecb0511c23c4710eec78fa2b50e68aaddf79bcac

Tx prefix hash: f0fea10fe10f2d9ef5e9b116342148279710f26db8a3480c2e7cd4258a11fccb
Tx public key: ef4b55890cebe383f9710adeefb8dd6a9ae80fb089533a4b72301fb1c4c9f11d
Timestamp: 1705185145 Timestamp [UCT]: 2024-01-13 22:32:25 Age [y:d:h:m:s]: 01:122:17:43:36
Block: 934716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348850 RingCT/type: yes/0
Extra: 01ef4b55890cebe383f9710adeefb8dd6a9ae80fb089533a4b72301fb1c4c9f11d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2384aa522917d55ad08cec27528afae17c7cd09b2cd4532793ac3dab5da550c2 0.600000000000 1392732 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": 934726, "vin": [ { "gen": { "height": 934716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2384aa522917d55ad08cec27528afae17c7cd09b2cd4532793ac3dab5da550c2" } } ], "extra": [ 1, 239, 75, 85, 137, 12, 235, 227, 131, 249, 113, 10, 222, 239, 184, 221, 106, 154, 232, 15, 176, 137, 83, 58, 75, 114, 48, 31, 177, 196, 201, 241, 29, 2, 17, 0, 0, 0, 4, 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