Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed5b7f3a60c69f268362ae3b8bc0cadc4d681e623a742f0cf27052059769305

Tx prefix hash: b7d95bfdfea950f651171a07a0486d05d2fc2646d2bbe3ac9f9fc6ab6ae863d9
Tx public key: 0fe772f55cd4d7ad11386c13d0e68ad580a0cbb51b69f31a46af253ae1f65615
Timestamp: 1709961988 Timestamp [UCT]: 2024-03-09 05:26:28 Age [y:d:h:m:s]: 01:013:10:39:16
Block: 974341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270602 RingCT/type: yes/0
Extra: 010fe772f55cd4d7ad11386c13d0e68ad580a0cbb51b69f31a46af253ae1f656150211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 705b29acfbb977fdaf16b9927272e6dc95a15bcd2ac096b0d6da3d5b89adaad4 0.600000000000 1434296 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": 974351, "vin": [ { "gen": { "height": 974341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "705b29acfbb977fdaf16b9927272e6dc95a15bcd2ac096b0d6da3d5b89adaad4" } } ], "extra": [ 1, 15, 231, 114, 245, 92, 212, 215, 173, 17, 56, 108, 19, 208, 230, 138, 213, 128, 160, 203, 181, 27, 105, 243, 26, 70, 175, 37, 58, 225, 246, 86, 21, 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