Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9959b884089ac2e8fa2eb701ac849b398ca053484e07549b5d1757ad0d148a

Tx prefix hash: 680bc39f6b642bf8891f66de79f57ce8f9ca69f222ee3fd1c94f061c3d5c3791
Tx public key: f6311220a8a94888e5ba9b2cf6d40b0156d48df4c3b04d941a90257c56f48374
Timestamp: 1673619700 Timestamp [UCT]: 2023-01-13 14:21:40 Age [y:d:h:m:s]: 02:149:08:17:40
Block: 673901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 628456 RingCT/type: yes/0
Extra: 01f6311220a8a94888e5ba9b2cf6d40b0156d48df4c3b04d941a90257c56f483740211000000025029cbac000000000000000000

1 output(s) for total of 3.589931724000 dcy

stealth address amount amount idx
00: b6c258260de7d248c3c4a64cd54170891476c288e8ce7d593e22e10327ffe028 3.589931724000 1115530 of 0

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": 673911, "vin": [ { "gen": { "height": 673901 } } ], "vout": [ { "amount": 3589931724, "target": { "key": "b6c258260de7d248c3c4a64cd54170891476c288e8ce7d593e22e10327ffe028" } } ], "extra": [ 1, 246, 49, 18, 32, 168, 169, 72, 136, 229, 186, 155, 44, 246, 212, 11, 1, 86, 212, 141, 244, 195, 176, 77, 148, 26, 144, 37, 124, 86, 244, 131, 116, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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