Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aa11f01f770f8870d8f3c29555096ee280d28310a26243912402a0029135591

Tx prefix hash: 04407eb5eb84ea61dd5551df7c9806f243b718f4b318cc1b75904e24782827a4
Tx public key: 1fcc72f18caf688b3f05eb6dc30f733eb25fec29ea980d6c67993e207c821f16
Timestamp: 1731216528 Timestamp [UCT]: 2024-11-10 05:28:48 Age [y:d:h:m:s]: 00:132:10:51:22
Block: 1150472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94479 RingCT/type: yes/0
Extra: 011fcc72f18caf688b3f05eb6dc30f733eb25fec29ea980d6c67993e207c821f160211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b32d0e23d9c1f3dd2a0f0237b4d0ea2edd955fe2e11555fc4a67afd6875f822 0.600000000000 1635793 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": 1150482, "vin": [ { "gen": { "height": 1150472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b32d0e23d9c1f3dd2a0f0237b4d0ea2edd955fe2e11555fc4a67afd6875f822" } } ], "extra": [ 1, 31, 204, 114, 241, 140, 175, 104, 139, 63, 5, 235, 109, 195, 15, 115, 62, 178, 95, 236, 41, 234, 152, 13, 108, 103, 153, 62, 32, 124, 130, 31, 22, 2, 17, 0, 0, 0, 1, 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