Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 949e6a170cd1d0b9c4438d3292a7c33f48066495ff2ef3ab525043e8bc647c37

Tx prefix hash: fd59e61406e1bc05fc9bdf59e1c69a23ef0115358e967466fbb490142bb2c454
Tx public key: dc696fdd3c50498062e4a934eaf0e9be0b0175e10bffa8a2788c608129c84ce0
Timestamp: 1702173806 Timestamp [UCT]: 2023-12-10 02:03:26 Age [y:d:h:m:s]: 01:037:18:59:12
Block: 909771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288361 RingCT/type: yes/0
Extra: 01dc696fdd3c50498062e4a934eaf0e9be0b0175e10bffa8a2788c608129c84ce00211000000034b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db990c4d659c5c0e4cb5fe1f4f871367b17994ca21ebe407a6b7e59e5c1b24f2 0.600000000000 1366890 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": 909781, "vin": [ { "gen": { "height": 909771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db990c4d659c5c0e4cb5fe1f4f871367b17994ca21ebe407a6b7e59e5c1b24f2" } } ], "extra": [ 1, 220, 105, 111, 221, 60, 80, 73, 128, 98, 228, 169, 52, 234, 240, 233, 190, 11, 1, 117, 225, 11, 255, 168, 162, 120, 140, 96, 129, 41, 200, 76, 224, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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