Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a71e4ba1efcfe97e1cffe8026f4aebabcf825f80b8449b369ad147f2e439ed

Tx prefix hash: 711db025241ef34503c03cebda75023af9fb1c4bd5aa1c6566e6709514f5c9ec
Tx public key: b7765886a236ba3928ad9e9f70c6b8d79639d39a8f405b971280cae710d137db
Timestamp: 1737793735 Timestamp [UCT]: 2025-01-25 08:28:55 Age [y:d:h:m:s]: 00:048:07:32:47
Block: 1204880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34352 RingCT/type: yes/0
Extra: 01b7765886a236ba3928ad9e9f70c6b8d79639d39a8f405b971280cae710d137db021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 702e22ee97c5d047d091579ea696c56f5f629d0696c0e8616c02eb341f9b9e04 0.600000000000 1691573 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": 1204890, "vin": [ { "gen": { "height": 1204880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "702e22ee97c5d047d091579ea696c56f5f629d0696c0e8616c02eb341f9b9e04" } } ], "extra": [ 1, 183, 118, 88, 134, 162, 54, 186, 57, 40, 173, 158, 159, 112, 198, 184, 215, 150, 57, 211, 154, 143, 64, 91, 151, 18, 128, 202, 231, 16, 209, 55, 219, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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