Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82966a740d5a558eb3a28254b70ddeaa0abccadc8f89e0b9864f9b4b1b4d6543

Tx prefix hash: 38778c4353f08d3ddb3ee45d9dab41a1ce9ea568f6391d356b7dae212d411fc0
Tx public key: 08046a40929d64db9bca2cc05b792a75a07cbe9faec9cf8db94172af6d68faac
Timestamp: 1705266508 Timestamp [UCT]: 2024-01-14 21:08:28 Age [y:d:h:m:s]: 01:322:19:31:38
Block: 935384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489579 RingCT/type: yes/0
Extra: 0108046a40929d64db9bca2cc05b792a75a07cbe9faec9cf8db94172af6d68faac0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b029c518244e575395a6cb59fd423b61f9757916ce37c23adae9959ba4a5740 0.600000000000 1393400 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": 935394, "vin": [ { "gen": { "height": 935384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b029c518244e575395a6cb59fd423b61f9757916ce37c23adae9959ba4a5740" } } ], "extra": [ 1, 8, 4, 106, 64, 146, 157, 100, 219, 155, 202, 44, 192, 91, 121, 42, 117, 160, 124, 190, 159, 174, 201, 207, 141, 185, 65, 114, 175, 109, 104, 250, 172, 2, 17, 0, 0, 0, 3, 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