Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30de6ecf3b8c42d693d818df9cf486b6f16c43370cc217c0f90c947cb65af8f3

Tx prefix hash: 2179f3142d552562dee88dea264cef699a5b96ce40fb6270338f7a88666cf1ed
Tx public key: 9816ad53c7924a7e71cf1711e78c5572b6f305c22c5c22bcb1638b9e0f025342
Timestamp: 1727050955 Timestamp [UCT]: 2024-09-23 00:22:35 Age [y:d:h:m:s]: 00:110:20:23:43
Block: 1116014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79249 RingCT/type: yes/0
Extra: 019816ad53c7924a7e71cf1711e78c5572b6f305c22c5c22bcb1638b9e0f025342021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e3da3b7c4a5736ac3e671630d890b62a8686555bba17559170bd9c99593e6d 0.600000000000 1596347 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": 1116024, "vin": [ { "gen": { "height": 1116014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e3da3b7c4a5736ac3e671630d890b62a8686555bba17559170bd9c99593e6d" } } ], "extra": [ 1, 152, 22, 173, 83, 199, 146, 74, 126, 113, 207, 23, 17, 231, 140, 85, 114, 182, 243, 5, 194, 44, 92, 34, 188, 177, 99, 139, 158, 15, 2, 83, 66, 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