Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 742e22fa3e59b7e86abed3e69775b7c4f212b38acaeb5f12a2b4e9cfe7005832

Tx prefix hash: 708d844dac5eb17428d495250a0f5333d0cab8e215994791b1fe5c366cde86e5
Tx public key: a8f7a012b2e9a81591a37d8dfea9184576205bc6d79556ae4f18f35438f22a03
Timestamp: 1717784184 Timestamp [UCT]: 2024-06-07 18:16:24 Age [y:d:h:m:s]: 01:154:08:33:19
Block: 1039190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368882 RingCT/type: yes/0
Extra: 01a8f7a012b2e9a81591a37d8dfea9184576205bc6d79556ae4f18f35438f22a030211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff0dde0d40ec5e8dc150cf527312e8a0fe70d8b9cdb38bf401a3c69b4886858e 0.600000000000 1507813 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": 1039200, "vin": [ { "gen": { "height": 1039190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff0dde0d40ec5e8dc150cf527312e8a0fe70d8b9cdb38bf401a3c69b4886858e" } } ], "extra": [ 1, 168, 247, 160, 18, 178, 233, 168, 21, 145, 163, 125, 141, 254, 169, 24, 69, 118, 32, 91, 198, 215, 149, 86, 174, 79, 24, 243, 84, 56, 242, 42, 3, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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