Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd31456068a29aff93c0a6da73f7732f87d5803d1845f54c484d840fefe7c1be

Tx prefix hash: fe2d0e47ff3814471d2be0248521e1ee1393286debc02fe4981315ff68ab126a
Tx public key: cfbab64d0fb5364a6095aefb2a14e23f6a4eb3c9e68ccfbf877030a0ebc1d64b
Timestamp: 1735606360 Timestamp [UCT]: 2024-12-31 00:52:40 Age [y:d:h:m:s]: 00:321:04:55:03
Block: 1186810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227077 RingCT/type: yes/0
Extra: 01cfbab64d0fb5364a6095aefb2a14e23f6a4eb3c9e68ccfbf877030a0ebc1d64b02110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e811ab2d158fb79d1402abf5362310a08148eb810d129744e5d40b7b5f5848 0.600000000000 1673295 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": 1186820, "vin": [ { "gen": { "height": 1186810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e811ab2d158fb79d1402abf5362310a08148eb810d129744e5d40b7b5f5848" } } ], "extra": [ 1, 207, 186, 182, 77, 15, 181, 54, 74, 96, 149, 174, 251, 42, 20, 226, 63, 106, 78, 179, 201, 230, 140, 207, 191, 135, 112, 48, 160, 235, 193, 214, 75, 2, 17, 0, 0, 0, 13, 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