Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23bd59b51d7f5bf72f0625ed0f89a4cd3dd2a2ba73dfb242f7cb12e65f786d71

Tx prefix hash: c0173837f40d02a8ba864cb1ba13a031acad58ecc68e0413898a5fb9e62b100e
Tx public key: d5ed421b782c2d878dca2ef4a7bae5f487b24258861dfcf081f44ba9d1ea738e
Timestamp: 1709017836 Timestamp [UCT]: 2024-02-27 07:10:36 Age [y:d:h:m:s]: 01:076:03:16:12
Block: 966514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315450 RingCT/type: yes/0
Extra: 01d5ed421b782c2d878dca2ef4a7bae5f487b24258861dfcf081f44ba9d1ea738e021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32ad1197d5f8e338462e7d987c325ceb72003864c03da02a9df6d4b9a4aac1f1 0.600000000000 1426273 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": 966524, "vin": [ { "gen": { "height": 966514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32ad1197d5f8e338462e7d987c325ceb72003864c03da02a9df6d4b9a4aac1f1" } } ], "extra": [ 1, 213, 237, 66, 27, 120, 44, 45, 135, 141, 202, 46, 244, 167, 186, 229, 244, 135, 178, 66, 88, 134, 29, 252, 240, 129, 244, 75, 169, 209, 234, 115, 142, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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