Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c2deb219d2a2c1645192d118c4d4dc5b3e0a83ca81999ee795876d63ddc132

Tx prefix hash: 36ea4d9fb96deef9891005ce263c3e4338df04b94dc1ee0de7cda70e3213a2cb
Tx public key: fe447666d04943923d54377b42725c26544233b36f5c6c1eb3d459600e65df33
Timestamp: 1726473692 Timestamp [UCT]: 2024-09-16 08:01:32 Age [y:d:h:m:s]: 00:116:20:32:56
Block: 1111223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83566 RingCT/type: yes/0
Extra: 01fe447666d04943923d54377b42725c26544233b36f5c6c1eb3d459600e65df33021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e7d86c6f180c60e1ca940a9f9557baf5fe0c857a66cdecc807f2930b33e5e22 0.600000000000 1590106 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": 1111233, "vin": [ { "gen": { "height": 1111223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e7d86c6f180c60e1ca940a9f9557baf5fe0c857a66cdecc807f2930b33e5e22" } } ], "extra": [ 1, 254, 68, 118, 102, 208, 73, 67, 146, 61, 84, 55, 123, 66, 114, 92, 38, 84, 66, 51, 179, 111, 92, 108, 30, 179, 212, 89, 96, 14, 101, 223, 51, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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