Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe4d4dbafb0046e356ab62b144c367c2f29488e8b05531769b7f4c9ef99119d

Tx prefix hash: 130c1e4fd0315f66028894a38ca489f0b0ec3af1528ed73e1cef2cbf91c61080
Tx public key: 9e86e876c0795aa763011cc40ba202c9c35d79a3e5fb1549b3f671efca7351e2
Timestamp: 1711098894 Timestamp [UCT]: 2024-03-22 09:14:54 Age [y:d:h:m:s]: 01:224:00:23:56
Block: 983781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418802 RingCT/type: yes/0
Extra: 019e86e876c0795aa763011cc40ba202c9c35d79a3e5fb1549b3f671efca7351e20211000000070011055b000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 837a26d8665acb510eaab9f58f492ab5ab5e26cd02c9e4bbc48b77f1737998e1 0.600010000000 1443926 of 0

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": 983791, "vin": [ { "gen": { "height": 983781 } } ], "vout": [ { "amount": 600010000, "target": { "key": "837a26d8665acb510eaab9f58f492ab5ab5e26cd02c9e4bbc48b77f1737998e1" } } ], "extra": [ 1, 158, 134, 232, 118, 192, 121, 90, 167, 99, 1, 28, 196, 11, 162, 2, 201, 195, 93, 121, 163, 229, 251, 21, 73, 179, 246, 113, 239, 202, 115, 81, 226, 2, 17, 0, 0, 0, 7, 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