Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9dff3c2c5a0f221514f5badf7b72918f68f12edc67870dc2ba4fb70ed11f513

Tx prefix hash: ca44d691985849ffde932e3a97c3b279a774d14ed8007dfcf12679a5a4ac4e32
Tx public key: f7aa9e154d350a429fd33826a0e415ae3c47e8761473bd17207155125e10a720
Timestamp: 1707652442 Timestamp [UCT]: 2024-02-11 11:54:02 Age [y:d:h:m:s]: 00:314:04:29:29
Block: 955182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224971 RingCT/type: yes/0
Extra: 01f7aa9e154d350a429fd33826a0e415ae3c47e8761473bd17207155125e10a72002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a89b2cc0fcd71ef5c98e11cd2383e6bd59efd2ecd365dac5a462e8f7b84cae36 0.600000000000 1414468 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": 955192, "vin": [ { "gen": { "height": 955182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a89b2cc0fcd71ef5c98e11cd2383e6bd59efd2ecd365dac5a462e8f7b84cae36" } } ], "extra": [ 1, 247, 170, 158, 21, 77, 53, 10, 66, 159, 211, 56, 38, 160, 228, 21, 174, 60, 71, 232, 118, 20, 115, 189, 23, 32, 113, 85, 18, 94, 16, 167, 32, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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