Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46b43cbce4f030c7c1ac93a9a250ac5db0d9d4607e83a3015cb6dc5553d81bb

Tx prefix hash: c0ecf589cffe3c6821754c00165f9e4745c73d1836cabdd4a5143dea7219e5e4
Tx public key: 1f0bb0d76fdca9bbd06654bc63598a4571b4f2d4c0ca1bfbb3fd8926f45de2cf
Timestamp: 1721278939 Timestamp [UCT]: 2024-07-18 05:02:19 Age [y:d:h:m:s]: 00:129:02:17:22
Block: 1068175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92358 RingCT/type: yes/0
Extra: 011f0bb0d76fdca9bbd06654bc63598a4571b4f2d4c0ca1bfbb3fd8926f45de2cf021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 784ba6b0dc64c85a084b2ee22f19b19c1060d9a8ca381dfb2e4075348784851f 0.600000000000 1539220 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": 1068185, "vin": [ { "gen": { "height": 1068175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "784ba6b0dc64c85a084b2ee22f19b19c1060d9a8ca381dfb2e4075348784851f" } } ], "extra": [ 1, 31, 11, 176, 215, 111, 220, 169, 187, 208, 102, 84, 188, 99, 89, 138, 69, 113, 180, 242, 212, 192, 202, 27, 251, 179, 253, 137, 38, 244, 93, 226, 207, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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