Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9b4c1b14fa647e91becd797ef064d0252cee95cc4f753fa474ce48bdc9a7df2

Tx prefix hash: 37c8f73f4df10d730cde84de79d7207bc7480a095b5f5c8d75a26c17f0c818a6
Tx public key: d4ca52ef8670316b1ec329b55a081f014f34901fa88e5aea909cd26a7b0eb0e0
Timestamp: 1724090181 Timestamp [UCT]: 2024-08-19 17:56:21 Age [y:d:h:m:s]: 00:137:16:41:57
Block: 1091474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98502 RingCT/type: yes/0
Extra: 01d4ca52ef8670316b1ec329b55a081f014f34901fa88e5aea909cd26a7b0eb0e002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2936efda14393d1c247c061e5b0bd94e9a2d73500b59f52ae104d45e3a62922c 0.600000000000 1566107 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": 1091484, "vin": [ { "gen": { "height": 1091474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2936efda14393d1c247c061e5b0bd94e9a2d73500b59f52ae104d45e3a62922c" } } ], "extra": [ 1, 212, 202, 82, 239, 134, 112, 49, 107, 30, 195, 41, 181, 90, 8, 31, 1, 79, 52, 144, 31, 168, 142, 90, 234, 144, 156, 210, 106, 123, 14, 176, 224, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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