Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52a307df50d89d7a817bc9af69c8f79ec101bda4ffb9208af0c6070d2403e948

Tx prefix hash: 2b0ed74232a4e2a5ec1debb0a731726b1af7c096f7a7de4093438933128afb88
Tx public key: e8b5f5fee8a67dfd6b973d9dcc7e28359d590b49f6e67b7ac1edf30881a0b376
Timestamp: 1727195216 Timestamp [UCT]: 2024-09-24 16:26:56 Age [y:d:h:m:s]: 00:223:06:24:51
Block: 1117204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159398 RingCT/type: yes/0
Extra: 01e8b5f5fee8a67dfd6b973d9dcc7e28359d590b49f6e67b7ac1edf30881a0b376021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b99590e588f3d4a7fe123ecc5760bcea22a64f37970cfba1fd03a8e3e1321f7 0.600000000000 1597961 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": 1117214, "vin": [ { "gen": { "height": 1117204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b99590e588f3d4a7fe123ecc5760bcea22a64f37970cfba1fd03a8e3e1321f7" } } ], "extra": [ 1, 232, 181, 245, 254, 232, 166, 125, 253, 107, 151, 61, 157, 204, 126, 40, 53, 157, 89, 11, 73, 246, 230, 123, 122, 193, 237, 243, 8, 129, 160, 179, 118, 2, 17, 0, 0, 0, 3, 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