Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe9196861480c78e7b1dd9efa31c29cdc5c9a89a306ab5a3e35656ba9bc70b7

Tx prefix hash: f752e13f6bcef92fa678b44eb377f69708e2207d3c97846b21697f86d5a5f6ab
Tx public key: b3741aaec45454a87f9605dc51c5c573dd19ae6b8783dccd27afd712c2aa25aa
Timestamp: 1724771969 Timestamp [UCT]: 2024-08-27 15:19:29 Age [y:d:h:m:s]: 00:228:03:18:58
Block: 1097109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162920 RingCT/type: yes/0
Extra: 01b3741aaec45454a87f9605dc51c5c573dd19ae6b8783dccd27afd712c2aa25aa02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d765a9957a6d3b47bd1416fc56aebbb91250afa97cc19c23d6da6aff473552a 0.600000000000 1572410 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": 1097119, "vin": [ { "gen": { "height": 1097109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d765a9957a6d3b47bd1416fc56aebbb91250afa97cc19c23d6da6aff473552a" } } ], "extra": [ 1, 179, 116, 26, 174, 196, 84, 84, 168, 127, 150, 5, 220, 81, 197, 197, 115, 221, 25, 174, 107, 135, 131, 220, 205, 39, 175, 215, 18, 194, 170, 37, 170, 2, 17, 0, 0, 0, 14, 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