Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d1c5b2faa4cbbc1618f7fba3f66163f4b6817c67926183bffd7758aab9c409e

Tx prefix hash: 8049c9f546a2b469ba3df7d3f25ad2ae8c4f9765e551c3ebc6fa030b221efc1d
Tx public key: 652d0597a2cb31c29c2babe7abfb2a3f537654d4fb25f6be5a2640119af892fd
Timestamp: 1718921847 Timestamp [UCT]: 2024-06-20 22:17:27 Age [y:d:h:m:s]: 01:193:16:35:18
Block: 1048610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397056 RingCT/type: yes/0
Extra: 01652d0597a2cb31c29c2babe7abfb2a3f537654d4fb25f6be5a2640119af892fd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76114f8129c5b1e2830ab43735c800dd7ac205e82af45723df85cf22ee1df5b 0.600000000000 1518695 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": 1048620, "vin": [ { "gen": { "height": 1048610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76114f8129c5b1e2830ab43735c800dd7ac205e82af45723df85cf22ee1df5b" } } ], "extra": [ 1, 101, 45, 5, 151, 162, 203, 49, 194, 156, 43, 171, 231, 171, 251, 42, 63, 83, 118, 84, 212, 251, 37, 246, 190, 90, 38, 64, 17, 154, 248, 146, 253, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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