Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c88b6eb80e0f7b213c0ab0cb62a29df2290e53f9ecd406dbcdbbfb48abcd839a

Tx prefix hash: 73b81bd9e335463c639a592e792e2d0e9e87cfdff05bd521d4173a9301df8e50
Tx public key: dcc288f70e9c8cf3f44b66736400d10f209859c78a2a39bfa55e208f35c54e67
Timestamp: 1727712212 Timestamp [UCT]: 2024-09-30 16:03:32 Age [y:d:h:m:s]: 00:227:05:55:59
Block: 1121496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162235 RingCT/type: yes/0
Extra: 01dcc288f70e9c8cf3f44b66736400d10f209859c78a2a39bfa55e208f35c54e6702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08c618fc7495de149850b354334975d75d2d3cd1ae8eeb46e1f69bf99a93c8af 0.600000000000 1603781 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": 1121506, "vin": [ { "gen": { "height": 1121496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08c618fc7495de149850b354334975d75d2d3cd1ae8eeb46e1f69bf99a93c8af" } } ], "extra": [ 1, 220, 194, 136, 247, 14, 156, 140, 243, 244, 75, 102, 115, 100, 0, 209, 15, 32, 152, 89, 199, 138, 42, 57, 191, 165, 94, 32, 143, 53, 197, 78, 103, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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