Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335651946b47cec02728612effb9ac4db276f060fc63ad6a3505e8e99c179e64

Tx prefix hash: 3e81fc92a44b99a83eea2b3667b3875a87fb92063b276132a5207194ad7bfcd9
Tx public key: d35f2aa861e667f5cc04d9ba0c5ebe8a4b25bf623fc769b3ab2614884fe8c8a0
Timestamp: 1719600276 Timestamp [UCT]: 2024-06-28 18:44:36 Age [y:d:h:m:s]: 00:286:08:59:33
Block: 1054234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204638 RingCT/type: yes/0
Extra: 01d35f2aa861e667f5cc04d9ba0c5ebe8a4b25bf623fc769b3ab2614884fe8c8a002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9325bb8b674fbd27c71c3a35fd2ab6cf2cc4cbf9fd0667ca88425c907f15398c 0.600000000000 1524595 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": 1054244, "vin": [ { "gen": { "height": 1054234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9325bb8b674fbd27c71c3a35fd2ab6cf2cc4cbf9fd0667ca88425c907f15398c" } } ], "extra": [ 1, 211, 95, 42, 168, 97, 230, 103, 245, 204, 4, 217, 186, 12, 94, 190, 138, 75, 37, 191, 98, 63, 199, 105, 179, 171, 38, 20, 136, 79, 232, 200, 160, 2, 17, 0, 0, 0, 1, 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