Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a5434d85c4f3d22d0b99addb1c0b744256d8d2610836a9697f29d63ea17f08

Tx prefix hash: f5c1de7886783aa20ca249d770116992b21018d03ba473af8aae56343bb06220
Tx public key: 04226ece6f90548b1f814da8a277db9b5971cf2fda9f883ff42f0089d3dfc434
Timestamp: 1733097148 Timestamp [UCT]: 2024-12-01 23:52:28 Age [y:d:h:m:s]: 00:339:13:50:01
Block: 1166037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240193 RingCT/type: yes/0
Extra: 0104226ece6f90548b1f814da8a277db9b5971cf2fda9f883ff42f0089d3dfc434021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78d8cc87232cf30c08e84b48d763cd14e006254d07d1c37e5e745c3691ef7087 0.600000000000 1651714 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": 1166047, "vin": [ { "gen": { "height": 1166037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d8cc87232cf30c08e84b48d763cd14e006254d07d1c37e5e745c3691ef7087" } } ], "extra": [ 1, 4, 34, 110, 206, 111, 144, 84, 139, 31, 129, 77, 168, 162, 119, 219, 155, 89, 113, 207, 47, 218, 159, 136, 63, 244, 47, 0, 137, 211, 223, 196, 52, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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