Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9bc9d83b6c4bb22fbf3d77bab3e955442acfe159acf062a14753463b888dbc6

Tx prefix hash: 622f1b73ccdb23a0e7059588c5e975d6781a58a2b175b032fbbdaffe8e6aeac1
Tx public key: e50a58bb89109a1a6dcafdad89f3108790e6af27f062f563aa57ae36cf51a867
Timestamp: 1710436938 Timestamp [UCT]: 2024-03-14 17:22:18 Age [y:d:h:m:s]: 00:328:00:47:22
Block: 978297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234513 RingCT/type: yes/0
Extra: 01e50a58bb89109a1a6dcafdad89f3108790e6af27f062f563aa57ae36cf51a8670211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32716bcbf9e3bbf3d3c6ef6fdc2a0e7127e3444b137d1e8c34725bcfddd4af62 0.600000000000 1438320 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": 978307, "vin": [ { "gen": { "height": 978297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32716bcbf9e3bbf3d3c6ef6fdc2a0e7127e3444b137d1e8c34725bcfddd4af62" } } ], "extra": [ 1, 229, 10, 88, 187, 137, 16, 154, 26, 109, 202, 253, 173, 137, 243, 16, 135, 144, 230, 175, 39, 240, 98, 245, 99, 170, 87, 174, 54, 207, 81, 168, 103, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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