Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d65061d19f5bf756ea3ca90c6720e5ed45bf9b0fdc5f502050e72baa0aabc25

Tx prefix hash: 5e2cedf0ed71af750dfb4fb86bbf36ed6920b57acb39277b71f87ad8ce870f9b
Tx public key: 04135db1774be358191df42a21449b11bba8d3d3c799779932e6cefd6b49c8f3
Timestamp: 1724143899 Timestamp [UCT]: 2024-08-20 08:51:39 Age [y:d:h:m:s]: 00:281:16:33:02
Block: 1091919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201229 RingCT/type: yes/0
Extra: 0104135db1774be358191df42a21449b11bba8d3d3c799779932e6cefd6b49c8f3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87a18cf666dbe22b20d1f7ad36b667a9b037dde0a5da1cacca0c40d5c3c99a7b 0.600000000000 1566556 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": 1091929, "vin": [ { "gen": { "height": 1091919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87a18cf666dbe22b20d1f7ad36b667a9b037dde0a5da1cacca0c40d5c3c99a7b" } } ], "extra": [ 1, 4, 19, 93, 177, 119, 75, 227, 88, 25, 29, 244, 42, 33, 68, 155, 17, 187, 168, 211, 211, 199, 153, 119, 153, 50, 230, 206, 253, 107, 73, 200, 243, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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