Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2a3351ff78bd2aa99123ee429da35b64b81b7f9847cfc7ceda7e9d5ab737ca7

Tx prefix hash: 2f8822d1b6e80cbf579f6855d923cc3747053e21729d4bb249b3b9f2877ad50e
Tx public key: d884f9d952a5483f7659a4a5397b9fdb3c537938d7008d3a39391f98152ad5fc
Timestamp: 1734528333 Timestamp [UCT]: 2024-12-18 13:25:33 Age [y:d:h:m:s]: 00:319:20:05:02
Block: 1177923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226052 RingCT/type: yes/0
Extra: 01d884f9d952a5483f7659a4a5397b9fdb3c537938d7008d3a39391f98152ad5fc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dba9d389f48f69ea4e30902be120431efc7560b21df209da14b6db9357f821cf 0.600000000000 1664304 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": 1177933, "vin": [ { "gen": { "height": 1177923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dba9d389f48f69ea4e30902be120431efc7560b21df209da14b6db9357f821cf" } } ], "extra": [ 1, 216, 132, 249, 217, 82, 165, 72, 63, 118, 89, 164, 165, 57, 123, 159, 219, 60, 83, 121, 56, 215, 0, 141, 58, 57, 57, 31, 152, 21, 42, 213, 252, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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