Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75f708f815385978c8509a544153cca3c8c1d221cca8193bbe07f7bda5874ac

Tx prefix hash: b3ae7120031474163a47b4ae82a7e074c60a7028035a08edb732b083c82695ce
Tx public key: 86e31b6d5aa12fa2c935f1b47bde27064e5ce8ab167203ac1d963c60819b1fdd
Timestamp: 1715950894 Timestamp [UCT]: 2024-05-17 13:01:34 Age [y:d:h:m:s]: 00:251:09:35:12
Block: 1023985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179877 RingCT/type: yes/0
Extra: 0186e31b6d5aa12fa2c935f1b47bde27064e5ce8ab167203ac1d963c60819b1fdd02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 539da55f6e174ca3cd29b94a9bc9057d7439753a4b25e780b5d0fa7a9ef6d4aa 0.600000000000 1489378 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": 1023995, "vin": [ { "gen": { "height": 1023985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "539da55f6e174ca3cd29b94a9bc9057d7439753a4b25e780b5d0fa7a9ef6d4aa" } } ], "extra": [ 1, 134, 227, 27, 109, 90, 161, 47, 162, 201, 53, 241, 180, 123, 222, 39, 6, 78, 92, 232, 171, 22, 114, 3, 172, 29, 150, 60, 96, 129, 155, 31, 221, 2, 17, 0, 0, 0, 3, 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