Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa41a6b1ae686ac4fc453d4c9490d264adf832342a65b10da7f56be42b70e676

Tx prefix hash: f32308b576ab707782f6011c9b30edf27c520473cfee4b1b4eac869f8cb7fe44
Tx public key: 0b003102cbd9cc6a252265fd69816c81a41b8173865e8f81f94fd75a11797bee
Timestamp: 1679496096 Timestamp [UCT]: 2023-03-22 14:41:36 Age [y:d:h:m:s]: 02:049:22:58:29
Block: 722660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557247 RingCT/type: yes/0
Extra: 010b003102cbd9cc6a252265fd69816c81a41b8173865e8f81f94fd75a11797bee021100000005faf35c9c000000000000000000

1 output(s) for total of 2.474727074000 dcy

stealth address amount amount idx
00: 0736a9caaa233a1673a6da01c8f7014c631d47eb467934a73b8d204845a68a99 2.474727074000 1167603 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": 722670, "vin": [ { "gen": { "height": 722660 } } ], "vout": [ { "amount": 2474727074, "target": { "key": "0736a9caaa233a1673a6da01c8f7014c631d47eb467934a73b8d204845a68a99" } } ], "extra": [ 1, 11, 0, 49, 2, 203, 217, 204, 106, 37, 34, 101, 253, 105, 129, 108, 129, 164, 27, 129, 115, 134, 94, 143, 129, 249, 79, 215, 90, 17, 121, 123, 238, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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