Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1f3fc0645bfe4803fe44a1282702f4a44367acb1c387ebb9c860ec4fa0800c

Tx prefix hash: 592b3e9754a209e5f930bf3ca4f33bb1cb144f8796f8c19358f9eddc567f5314
Tx public key: 9f831db1a9f1cc8d46630805a49528dcb3695f279b4b74453530da18f272bcb9
Timestamp: 1729074811 Timestamp [UCT]: 2024-10-16 10:33:31 Age [y:d:h:m:s]: 00:149:05:02:19
Block: 1132808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106406 RingCT/type: yes/0
Extra: 019f831db1a9f1cc8d46630805a49528dcb3695f279b4b74453530da18f272bcb90211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd1a1ec7cde81a2b5b8d06afb33f0d129f1445f170e18948f49896e0fc505096 0.600000000000 1615811 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": 1132818, "vin": [ { "gen": { "height": 1132808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd1a1ec7cde81a2b5b8d06afb33f0d129f1445f170e18948f49896e0fc505096" } } ], "extra": [ 1, 159, 131, 29, 177, 169, 241, 204, 141, 70, 99, 8, 5, 164, 149, 40, 220, 179, 105, 95, 39, 155, 75, 116, 69, 53, 48, 218, 24, 242, 114, 188, 185, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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