Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dafaee75aa1110deadf7f23780c577e3b18126a4166fb5c6b5937fccd4fe4443

Tx prefix hash: c2c7c0643259490fd0f21b45cbd7b404714c519807f5b5c0285c93e80e8a3d65
Tx public key: 2db5b2c0fd801ea16c144462c33273f6918d8ec82bb2cd2b4121746a25c225db
Timestamp: 1736517582 Timestamp [UCT]: 2025-01-10 13:59:42 Age [y:d:h:m:s]: 00:082:13:28:42
Block: 1194351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58778 RingCT/type: yes/0
Extra: 012db5b2c0fd801ea16c144462c33273f6918d8ec82bb2cd2b4121746a25c225db0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2951c032168f157bd639541b8b067f18d936bff1edc31dafc21e9fba881cf105 0.600000000000 1680920 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": 1194361, "vin": [ { "gen": { "height": 1194351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2951c032168f157bd639541b8b067f18d936bff1edc31dafc21e9fba881cf105" } } ], "extra": [ 1, 45, 181, 178, 192, 253, 128, 30, 161, 108, 20, 68, 98, 195, 50, 115, 246, 145, 141, 142, 200, 43, 178, 205, 43, 65, 33, 116, 106, 37, 194, 37, 219, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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