Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b5b1892966a91e31934386f33b7e78404ceb749f096d24c9a71e476b9dd42ed

Tx prefix hash: 1f075f1c993a1eaf2229e2ce463ebd579ce5328afce4c390491a0ed15195de5e
Tx public key: bc2c2c5c483505d04290df09144b86e2668fa1a90e92c375dd94a4c5800df81e
Timestamp: 1707141488 Timestamp [UCT]: 2024-02-05 13:58:08 Age [y:d:h:m:s]: 01:094:08:13:42
Block: 950934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328510 RingCT/type: yes/0
Extra: 01bc2c2c5c483505d04290df09144b86e2668fa1a90e92c375dd94a4c5800df81e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1bfd1eb958f47a6218139e833401733ea397b70f8bc019334702f0c1e241880 0.600000000000 1409628 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": 950944, "vin": [ { "gen": { "height": 950934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1bfd1eb958f47a6218139e833401733ea397b70f8bc019334702f0c1e241880" } } ], "extra": [ 1, 188, 44, 44, 92, 72, 53, 5, 208, 66, 144, 223, 9, 20, 75, 134, 226, 102, 143, 161, 169, 14, 146, 195, 117, 221, 148, 164, 197, 128, 13, 248, 30, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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