Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fab8c219f38cadcc0def6128e24fa96b8dd060c094a2055d0e140c38b1ec38b

Tx prefix hash: e84b2800df14b46dc9648bf20e57cd1a7f3ba5102e71b64c80e34f5b82ea7854
Tx public key: 43312ad212660ddce9b5339799ffad68f8998679c61c67caa4f68a04284d7adc
Timestamp: 1706646624 Timestamp [UCT]: 2024-01-30 20:30:24 Age [y:d:h:m:s]: 01:066:16:03:20
Block: 946827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308721 RingCT/type: yes/0
Extra: 0143312ad212660ddce9b5339799ffad68f8998679c61c67caa4f68a04284d7adc0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7aafb9f4df24beb4a6443fc22dd25dcc24e7eb85d0c72c7b2acb42b760dd6c0 0.600000000000 1405167 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": 946837, "vin": [ { "gen": { "height": 946827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7aafb9f4df24beb4a6443fc22dd25dcc24e7eb85d0c72c7b2acb42b760dd6c0" } } ], "extra": [ 1, 67, 49, 42, 210, 18, 102, 13, 220, 233, 181, 51, 151, 153, 255, 173, 104, 248, 153, 134, 121, 198, 28, 103, 202, 164, 246, 138, 4, 40, 77, 122, 220, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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