Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3e34c94aff6a5ab401a5dfda0fc18cee95bf48be71e5865902f4a3e15a191b

Tx prefix hash: 06e0c0e64ad338cd81797a9bf2be7e1d42c85c85e3f2247cf46ac50a1e69e762
Tx public key: b5e2893bfe0d35f6c7858732b51b7b1ff4bea0e9112c2eaef4f026b69a9c0d98
Timestamp: 1726579260 Timestamp [UCT]: 2024-09-17 13:21:00 Age [y:d:h:m:s]: 00:178:12:41:49
Block: 1112102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127430 RingCT/type: yes/0
Extra: 01b5e2893bfe0d35f6c7858732b51b7b1ff4bea0e9112c2eaef4f026b69a9c0d98021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff93e292331491fcd9d07200ff686ff7f403e813f4455d13f49958361347504f 0.600000000000 1591303 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": 1112112, "vin": [ { "gen": { "height": 1112102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff93e292331491fcd9d07200ff686ff7f403e813f4455d13f49958361347504f" } } ], "extra": [ 1, 181, 226, 137, 59, 254, 13, 53, 246, 199, 133, 135, 50, 181, 27, 123, 31, 244, 190, 160, 233, 17, 44, 46, 174, 244, 240, 38, 182, 154, 156, 13, 152, 2, 17, 0, 0, 0, 3, 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