Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c75c99dc92bcade778387be0833e43f80ab093edc23db56dbbb9c02905f91b5

Tx prefix hash: 5bd35e7ef41af1cb87976247c15c6c765848012f5e53ad178e6eb0897e7fbad6
Tx public key: dc021182e94d92f8e3e3adf00df60d25c944f9c3ef917f63e1ae54683bd783d6
Timestamp: 1706540079 Timestamp [UCT]: 2024-01-29 14:54:39 Age [y:d:h:m:s]: 01:034:15:57:23
Block: 945941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285841 RingCT/type: yes/0
Extra: 01dc021182e94d92f8e3e3adf00df60d25c944f9c3ef917f63e1ae54683bd783d602110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9fb449769ba7c41a48a18ffcc1e870cd7bbec2c8187c94452c1de7a96013840 0.600000000000 1404271 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": 945951, "vin": [ { "gen": { "height": 945941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9fb449769ba7c41a48a18ffcc1e870cd7bbec2c8187c94452c1de7a96013840" } } ], "extra": [ 1, 220, 2, 17, 130, 233, 77, 146, 248, 227, 227, 173, 240, 13, 246, 13, 37, 201, 68, 249, 195, 239, 145, 127, 99, 225, 174, 84, 104, 59, 215, 131, 214, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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